12 research outputs found

    Rationale in Development Chat Messages: An Exploratory Study

    Full text link
    Chat messages of development teams play an increasingly significant role in software development, having replaced emails in some cases. Chat messages contain information about discussed issues, considered alternatives and argumentation leading to the decisions made during software development. These elements, defined as rationale, are invaluable during software evolution for documenting and reusing development knowledge. Rationale is also essential for coping with changes and for effective maintenance of the software system. However, exploiting the rationale hidden in the chat messages is challenging due to the high volume of unstructured messages covering a wide range of topics. This work presents the results of an exploratory study examining the frequency of rationale in chat messages, the completeness of the available rationale and the potential of automatic techniques for rationale extraction. For this purpose, we apply content analysis and machine learning techniques on more than 8,700 chat messages from three software development projects. Our results show that chat messages are a rich source of rationale and that machine learning is a promising technique for detecting rationale and identifying different rationale elements.Comment: 11 pages, 6 figures. The 14th International Conference on Mining Software Repositories (MSR'17

    Registry of Aortic Diseases to Model Adverse Events and Progression (ROADMAP) in Uncomplicated Type B Aortic Dissection: Study Design and Rationale

    Full text link
    PURPOSE To describe the design and methodological approach of a multicenter, retrospective study to externally validate a clinical and imaging-based model for predicting the risk of late adverse events in patients with initially uncomplicated type B aortic dissection (uTBAD). MATERIALS AND METHODS The Registry of Aortic Diseases to Model Adverse Events and Progression (ROADMAP) is a collaboration between 10 academic aortic centers in North America and Europe. Two centers have previously developed and internally validated a recently developed risk prediction model. Clinical and imaging data from eight ROADMAP centers will be used for external validation. Patients with uTBAD who survived the initial hospitalization between January 1, 2001, and December 31, 2013, with follow-up until 2020, will be retrospectively identified. Clinical and imaging data from the index hospitalization and all follow-up encounters will be collected at each center and transferred to the coordinating center for analysis. Baseline and follow-up CT scans will be evaluated by cardiovascular imaging experts using a standardized technique. RESULTS The primary end point is the occurrence of late adverse events, defined as aneurysm formation (≄6 cm), rapid expansion of the aorta (≄1 cm/y), fatal or nonfatal aortic rupture, new refractory pain, uncontrollable hypertension, and organ or limb malperfusion. The previously derived multivariable model will be externally validated by using Cox proportional hazards regression modeling. CONCLUSION This study will show whether a recent clinical and imaging-based risk prediction model for patients with uTBAD can be generalized to a larger population, which is an important step toward individualized risk stratification and therapy.Keywords: CT Angiography, Vascular, Aorta, Dissection, Outcomes Analysis, Aortic Dissection, MRI, TEVAR© RSNA, 2022See also the commentary by Rajiah in this issue

    An Exploratory Study of Twitter Messages about Software Applications

    Full text link
    Users of the Twitter microblogging platform share a considerable amount of information through short messages on a daily basis. Some of these so-called tweets discuss issues related to software and could include information that is relevant to the companies developing these applications. Such tweets have the potential to help requirements engineers better understand user needs and therefore provide important information for software evolution. However, little is known about the nature of tweets discussing software-related issues. In this paper, we report on the usage characteristics, content and automatic classification potential of tweets about software applications. Our results are based on an exploratory study in which we used descriptive statistics, content analysis, machine learning and lexical sentiment analysis to explore a dataset of 10,986,495 tweets about 30 different software applications. Our results show that searching for relevant information on software applications within the vast stream of tweets can be compared to looking for a needle in a haystack. However, this relevant information can provide valuable input for software companies and support the continuous evolution of the applications discussed in these tweets. Furthermore, our results show that it is possible to use machine learning and lexical sentiment analysis techniques to automatically extract information about the tweets regarding their relevance, authors and sentiment polarity

    A Needle in a Haystack: What Do Twitter Users Say about Software?

    Full text link
    Users of the Twitter microblogging platform share a vast amount of information about various topics through short messages on a daily basis. Some of these so called tweets include information that is relevant for software companies and could, for example, help requirements engineers to identify user needs. Therefore, tweets have the potential to aid in the continuous evolution of software applications. Despite the existence of such relevant tweets, little is known about their number and content. In this paper we report on the results of an exploratory study in which we analyzed the usage characteristics, content and automatic classification potential of tweets about software applications by using descriptive statistics, content analysis and machine learning techniques. Although the manual search of relevant information within the vast stream of tweets can be compared to looking for a needle in a haystack, our analysis shows that tweets provide a valuable input for software companies. Furthermore, our results demonstrate that machine learning techniques have the capacity to identify and harvest relevant information automatically

    Pandemic programming: How COVID-19 affects software developers and how their organizations can help

    Get PDF
    Context As a novel coronavirus swept the world in early 2020, thousands of software developers began working from home. Many did so on short notice, under difficult and stressful conditions. Objective This study investigates the effects of the pandemic on developers’ wellbeing and productivity. Method A questionnaire survey was created mainly from existing, validated scales and translated into 12 languages. The data was analyzed using non-parametric inferential statistics and structural equation modeling. Results The questionnaire received 2225 usable responses from 53 countries. Factor analysis supported the validity of the scales and the structural model achieved a good fit (CFI = 0.961, RMSEA = 0.051, SRMR = 0.067). Confirmatory results include: (1) the pandemic has had a negative effect on developers’ wellbeing and productivity; (2) productivity and wellbeing are closely related; (3) disaster preparedness, fear related to the pandemic and home office ergonomics all affect wellbeing or productivity. Exploratory analysis suggests that: (1) women, parents and people with disabilities may be disproportionately affected; (2) different people need different kinds of support

    Pandemic Programming: How COVID-19 affects software developers and how their organizations can help

    No full text
    Context. As a novel coronavirus swept the world in early 2020, thousands of software developers began working from home. Many did so on short notice, under difficult and stressful conditions. Objective. This study investigates the effects of the pandemic on developers' wellbeing and productivity. Method. A questionnaire survey was created mainly from existing, validated scales and translated into 12 languages. The data was analyzed using non-parametric inferential statistics and structural equation modeling. Results. The questionnaire received 2225 usable responses from 53 countries. Factor analysis supported the validity of the scales and the structural model achieved a good fit (CFI = 0.961, RMSEA = 0.051, SRMR = 0.067). Confirmatory results include: (1) the pandemic has had a negative effect on developers' wellbeing and productivity; (2) productivity and wellbeing are closely related; (3) disaster preparedness, fear related to the pandemic and home office ergonomics all affect wellbeing or productivity. Exploratory analysis suggests that: (1) women, parents and people with disabilities may be disproportionately affected; (2) different people need different kinds of support. Conclusions. To improve employee productivity, software companies should focus on maximizing employee wellbeing and improving the ergonomics of employees' home offices. Women, parents and disabled persons may require extra support

    Registry of Aortic Diseases to Model Adverse Events and Progression (ROADMAP) in Uncomplicated Type B Aortic Dissection:Study Design and Rationale

    No full text
    PURPOSE: To describe the design and methodological approach of a multicenter, retrospective study to externally validate a clinical and imaging-based model for predicting the risk of late adverse events in patients with initially uncomplicated type B aortic dissection (uTBAD). MATERIALS AND METHODS: The Registry of Aortic Diseases to Model Adverse Events and Progression (ROADMAP) is a collaboration between 10 academic aortic centers in North America and Europe. Two centers have previously developed and internally validated a recently developed risk prediction model. Clinical and imaging data from eight ROADMAP centers will be used for external validation. Patients with uTBAD who survived the initial hospitalization between January 1, 2001, and December 31, 2013, with follow-up until 2020, will be retrospectively identified. Clinical and imaging data from the index hospitalization and all follow-up encounters will be collected at each center and transferred to the coordinating center for analysis. Baseline and follow-up CT scans will be evaluated by cardiovascular imaging experts using a standardized technique. RESULTS: The primary end point is the occurrence of late adverse events, defined as aneurysm formation (≄6 cm), rapid expansion of the aorta (≄1 cm/y), fatal or nonfatal aortic rupture, new refractory pain, uncontrollable hypertension, and organ or limb malperfusion. The previously derived multivariable model will be externally validated by using Cox proportional hazards regression modeling. CONCLUSION: This study will show whether a recent clinical and imaging-based risk prediction model for patients with uTBAD can be generalized to a larger population, which is an important step toward individualized risk stratification and therapy.Keywords: CT Angiography, Vascular, Aorta, Dissection, Outcomes Analysis, Aortic Dissection, MRI, TEVAR© RSNA, 2022See also the commentary by Rajiah in this issue
    corecore